Issue to watch out for: coverlet-coverage/coverlet#1715

We don't collect code coverage data anyways, so this is more or less a non-issue.

CI uses

dotnet test --logger "junit;LogFileName=${{ matrix.configuration }}.xml" --results-directory test-results $env:Tests1 $env:Tests2 $env:Tests3

What are the respective equivalents for MTS?

See this thread on -logger: https://bsky.app/profile/tyrrrz.me/post/3liep5xqqy22q plus issue Tyrrrz/GitHubActionsTestLogger#41 (comment)

Edit: https://github.com/Tyrrrz/GitHubActionsTestLogger might be an option to add as well.

@christophwille Is it necessary to use junit test results format, or could you switch to TRX? Also, I'm not sure why you are passing individual dlls with $env:Tests1 etc. Why not simply run dotnet test on the whole solution? Like this:

dotnet test -- --report-trx --results-directory test-results

Note 1: You will need Microsoft.Testing.Extensions.TrxReport NuGet package for --report-trx to work.

Note 2: The extra -- will not be needed in the new dotnet test experience that is planned for .NET 10.

Small note: the abbreviation is MTP (Microsoft.Testing.Platform) not MTS

@christophwille Is it necessary to use junit test results format, or could you switch to TRX?

@Youssef1313 back in the day (at least) that was the reason (didn't check if that still is not trx-friendly). That is also the comment re:GitHubActionsTestLogger as a potential replacement.

Hmm, yeah looks like this GitHub Action doesn't support TRX: test-summary/action#1

I started a PR for the testlogger so that it supports JUnit reporter for MTP spekt/testlogger#172. Let's see if this can get merged soon, assuming the work is approved by the maintainer.

Things of note:

• https://github.com/dotnet/core/blob/main/release-notes/10.0/preview/preview3/sdk.md#support-for-microsoft-testing-platform-in-dotnet-test
• https://platform.uno/blog/microsoft-contributes-to-uno-platform-dramatically-reducing-testing-time/